fix(platform): port upload_artifact.py to mcp 2.x SDK - #185
Merged
Conversation
httpx2 client, 2-tuple streamable_http_client unpack, result.is_error; pin invocations to mcp[cli]>=2,<3 and dev group to mcp==2.0.0.
shafty023
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
plugins/platform/skills/upload-artifact/scripts/upload_artifact.pyfails at connect time against the current MCP Python SDK. The documented invocationuv run --with 'mcp[cli]'is unpinned and now resolves tomcp 2.0.0, where three 1.x-era shapes no longer hold:streamable_http_client(...)(read_stream, write_stream)result.isError(x4)result.is_error_build_http_clienthttpx.AsyncClienthttpx2.AsyncClient(httpxno longer pulled in)Change
httpx2client, 2-tuple unpack,result.is_error.mcp[cli]>=2,<3in the module docstring andSKILL.mdso it cannot drift again.list_projectsandupload) into one_connectasync context manager; theget-documenterror path now reuses_error_details.mcp==1.27.0->2.0.0(+uv lock) so pyright checks against the SDK the script actually requires. Nothing else in the repo importsmcp.platform1.1.3 -> 1.1.4, CHANGELOG entry.Verification
Live
MCPServerstreamable-http test server, script run end to end against it:--list-projects-> project list--verify-> round-trip lengths match--artifact-idversion +--verify-> round-trip lengths match{"error": "create-document-version failed", "details": [...]}, exit 1uv run ruff check .clean,uv run pyright0 errors,uv run pytest plugins/ -q2103 passed / 3 skipped.